home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20041116-20060924
/
000025_slash_dev_slas…_2000@yahoo.com_Thu Dec 16 14:50:40 2004.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Path: newsmaster.cc.columbia.edu!panix!newsfeed-00.mathworks.com!prodigy.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news.glorb.com!postnews.google.com!z14g2000cwz.googlegroups.com!not-for-mail
From: "Mark Sapiro" <slash_dev_slash_null_2000@yahoo.com>
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Long exit delay after file transfer to remote kermit
Date: 14 Dec 2004 20:46:42 -0800
Organization: http://groups.google.com
Lines: 39
Message-ID: <1103086002.362614.3770@z14g2000cwz.googlegroups.com>
References: <LYKdnfsEIoDD_CLcRVn-uQ@telcove.net>
NNTP-Posting-Host: 209.182.169.133
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1103086006 13498 127.0.0.1 (15 Dec 2004 04:46:46 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Wed, 15 Dec 2004 04:46:46 +0000 (UTC)
In-Reply-To: <LYKdnfsEIoDD_CLcRVn-uQ@telcove.net>
User-Agent: G2/0.2
Complaints-To: groups-abuse@google.com
Injection-Info: z14g2000cwz.googlegroups.com; posting-host=209.182.169.133;
posting-account=iQNWIg0AAAAD2fStXNC9nwGlPdSqjWrI
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15254
Mel wrote:
> I have a MS-DOS machine running MS-Kermit in server mode connected
via
> null-modem cable to a Win2000 machine running MS-Kermit in a DOS box.
I can
> transfer files fine to the DOS machine. I invoke kermit with:
>
> kermit send small.txt file1.txt, bye, exit
>
> and both machines do the transfer and return to the DOS prompt in 2-3
> seconds; but, when small.txt goes from a 30KB file to a 500KB file,
the
> return to DOS prompt takes around 60 seconds.
>
> Anyone know why the increased delay and how to eliminate it?
I think the likely explanation is that you have a large number of
sliding windows and a large packet size and the sender thinks it has
sent all the packets and shows 100%, but the server hasn't received,
stored and acked all the packets yet. This has to happen before the bye
and exit will occur.
Sixty seconds seems long, but if the MS-DOS machine is slow, it could
take that long.
If you notice that initially the transfer rate seems fast and then
suddenly slows after all the windows are in use, that is another
manifestation of this situation.
If you reduce the max number of windows and the packet size, the
transfer will probably take about the same total time, but it won't
seem to be done before it actually is.
--
Mark Sapiro msapiro at value net The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan